To ensure protection of your data, Double-Take Availability offers multi-level security using native operating system security features. Privileges are granted through membership in user groups defined on each machine running Double-Take Availability. To gain access to a particular Double-Take Availability source or target, the user must provide a valid operating system user name and password and the specified user name must be a member of one of the Double-Take Availability security groups. Once a valid user name and password have been provided and the Double-Take Availability source or target has verified membership in one of the Double-Take Availability security groups, the user is granted appropriate access to the source or target and the corresponding features are enabled in the client. Access to Double-Take Availability is granted on one of the following three levels.
The following table identifies which key Double-Take Availability features are available depending on the security access granted.
| Double-Take Availability Feature | Administrator Access |
Monitor Access |
|---|---|---|
| View replication sets and rules | X | X |
| Modify replication sets and rules | X | |
| View connections, mirroring, replication, verification, failover, and restoration | X | X |
| Control connections, mirroring, replication, verification, failover, and restoration | X | |
| View server settings | X | X |
| Modify server settings | X |
| Note: | Although Double-Take Availability passwords are encrypted when they are stored, Double-Take Availabilitysecurity design does assume that any machine running the Double-Take Availability client application is protected from unauthorized access. If you are running the Double-Take Availability client and step away from your machine, you must protect your machine from unauthorized access. |